Semgrep found 1 context-todo finding:

• pkg/scalers/azure_pipelines_scaler_test.go
  • L304 - Triage

Consider to use well-defined context

Semgrep found 1 no-direct-write-to-responsewriter finding:

• pkg/scalers/azure_pipelines_scaler_test.go
  • L343 - Triage

Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'.

Semgrep found 1 context-todo finding:

• pkg/scalers/azure_pipelines_scaler_test.go

  • L304 - Triage

Consider to use well-defined context

Ignore this finding from context-todo.
Semgrep found 1 no-direct-write-to-responsewriter finding:

• pkg/scalers/azure_pipelines_scaler_test.go

  • L343 - Triage

Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'.

Ignore this finding from no-direct-write-to-responsewriter.

I haven't changed this code, how should I go about resolving these semgrep issues?

Semgrep found 1 context-todo finding:

• pkg/scalers/azure_pipelines_scaler_test.go

  • L304 - Triage

Consider to use well-defined context
Ignore this finding from context-todo.
Semgrep found 1 no-direct-write-to-responsewriter finding:

• pkg/scalers/azure_pipelines_scaler_test.go

  • L343 - Triage

Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'.
Ignore this finding from no-direct-write-to-responsewriter.

I haven't changed this code, how should I go about resolving these semgrep issues?

Don't worry, I've ignored those findings for the PR and the check should pass now

/run-e2e pipeline
Update: You can check the progress here